home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group92c.txt
/
000087_icon-group-sender _Fri Nov 13 02:28:31 1992.msg
< prev
next >
Wrap
Internet Message Format
|
1993-01-04
|
1KB
Received: by cheltenham.cs.arizona.edu; Tue, 17 Nov 1992 05:49:07 MST
Date: 13 Nov 92 02:28:31 GMT
From: sun-barr!cs.utexas.edu!uwm.edu!linac!uchinews!ellis!goer@ames.arc.nasa.gov (Richard L. Goerwitz)
Organization: University of Chicago Computing Organizations
Subject: Re: Rationale for sortf() second argument?
Message-Id: <1992Nov13.022831.26740@midway.uchicago.edu>
References: <199211121658.AA02526@owl.cs.arizona.edu>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
"Gregg Townsend" <gmt@cs.arizona.edu> writes:
>
> Can someone explain to me why the second argument to the sortf() function
> is an integer index of the field in the record to sort on, instead of a
> string containing the field name?
>
>Not really. The awful truth is that I didn't even think of that when I wrote
>and contributed the implementation of sortf(). Your points are well taken.
Don't sell yourself short, Gregg. Integer offsets are much more general
than field names. They can be applied to lists as well as records. I'm
quite happy, myself, with how things worked out, although it's clear that
there are many possibilities for me to screw things up.
--
-Richard L. Goerwitz goer%midway@uchicago.bitnet
goer@midway.uchicago.edu rutgers!oddjob!ellis!goer